home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr25
/
inftxt.zip
/
WINOS2.TXT
< prev
next >
Wrap
Text File
|
1993-03-26
|
12KB
|
143 lines
PRINT SELECTION FOR APAR - II06062 92/07/14
APAR= II06062 SER= DD DOC
WINAP INFO APAR - GENERAL WINOS2 INFORMATION
( OS2WINAP OS2INFOAPAR WINOS2 R200 562107701 )
STAT= INTRAN FESN5NFO000-000 CTID= II0000 ISEV= 4
SB92/06/03 RC CL PD SEV= 4
PE= TYPE= I
RCOMP= INFOPCLIB PC LIB INFO ITE RREL= R001
FCOMP= PFREL= F TREL= T
ACTION= SEC/INT= DUP/
USPTF= PDPTF= DUPS 0
DW92/06/03 RT SC FT
RE PT UP LP
PV AP EN FL
LC92/06/22 RU92/06/03
CUST INST LVL/SU=
FAILING MODULE= FAILING LVL/SU=
SYSROUTE OF: RET APAR= PS=
COMP OPER ENV=
SYSRES= SYSIN= SYSOUT= CPU= RE-IPL=
OPTYPE= SPECIAL ACTIVITY= REGRESSION=
PRE-SCREEN NO.= RSCP= RS000
ERROR DESCRIPTION:
.
WINOS2 INFORMATION (WINAP ANALYST QUEUE)
========================================
These are the some of the more common problems related to
the use of Microsoft Windows (WINOS2) running under OS/2-2.0.
.
=== GENERAL WINDOWS INFORMATION ===
.
**Problem**
Windows 3.1 does not run under OS2-2.0.
**Solution**
Windows 3.10. Microsoft Windows 3.10 and some applications
that will only run with Windows Version 3.10 cannot run on
under OS/2-2.0. Windows 3.10 cannot be run either under a
OS/2-2.0 Dos Session or a OS/2-2.0 VMB. Windows Version 3.10
may be available under a future version of OS/2-2.0, but the
release date of this is unknown at this time.
.
**Problem**
Migrated Windows Applications do not run correctly.
**Solution**
The OS/2-2.0 Migration Utility does not migrate application
INI files. Some applications will not run correctly if settings
in either the WIN.INI or (app).INI file are not set correctly.
Therefore many of the initial problems users have with Windows
applications are because of the lack of INI files in the
OS2 MDOS WINOS2 directory. If the user installed OS/2-2.0 over
DOS/WIN 3.0 the new WIN.INI file in the WINOS2 directory should
be OK. If the user installed OS/2-2.0 over DOS/WIN 3.1 the
new WIN.INI file will not contain any settings from ther older
3.1 WIN.INI files. The easiest way to tell a user to correct
this problem is to reinstall the Windows Application from
using WINOS2. Another possible solution is to copy the
(app).INI file in the old windows directory to the WINOS2
directory.Coping the (app).INI file will not work in all
instances.
.
NOTE: The mini-applications supplied with Windows
3.1 will NOT work from any 3.0 environment, including
winos2. This is because these applications use new
features of Windows 3.1 not available in 3.0. By way of
example, 'Cardfile' will not run under winos2.
**Problem**
Full screen Window or Seamless Windows not starting. This
problem can be verified by typing WIN from a Full Screen DOS
session. This will show a Fatal Error 0x401 error.
**Solution**
This problem is caused by one of the drivers or sys files
listed in the Windows SYSTEM.INI file not loading correctly.
This could because the actual file is not present, or that
the driver does not fully load when Windows starts up. To
correct this problem the user can try reinstalling WINOS2
by doing a selective install of OS2. Another more timely
solution is to copy the SYSTEM.INI file in the WINOS2
directory to a printer and verify that each of the drivers or
system files actually exists.
.
CLIPBOARD PROBLEMS
.
**Problem**
The clipboard is extremely slow when running Windows. MS Excel
is exceeding slow when cutting or pasting to the clipboard.
**Solution**
Most applications that copy information to the clipboard copy
data in multiple formats. In the case of Excel, 16 different
formats. When the Windows clipboard is public, the computer
must do addtional conversion of data to the OS2 clipboard. The
solution to this is that if the customer can make the Windows
clipboard private, the speed of cutting and pasting will be no
different than that of normal Windows. The only problem with
this is that anything copied from the Windows session cannot be
pasted to OS2 unless clipboarddata is exported and when trying
to paste data copied from an OS2 session, another WINOS2 session
or a DOS Session, data must be imported. The only way to make
a WINOS2 seamless session private is to make a permanent change
removing lines starting the clipboard from the WINOS2 SYSTEM.INI
file. This is being worked on for a fix.
Remove !clipos2 from the 3 lines in the SYSTEM.INI..
**Problem**
NLS (National Language Support) OS/2-2.0 version cannot use
clipboard data when copying from PM or DOS and paste in Windows.
This problem has been verified in German and Swedish versions.
**Solution**
There is no workaround at this time. APAR# PJ04066.
.
=== DDE and OLE ===
.
**DDE Problems**
OLELIB.DLL and DDELIB.DLL dynamic libaries are not included with
OS/2-2.0. Some applications require these DLLs to use
OLE(Object linking and Embedding) or DDE(Dynamic Data Exchange).
**Solution**
Most applications using these DLLs include these DLLs on their
installation disk. These DLLs should be copied to the WINOS2
directory. These DLLs are included with Windows 3.1 and will
work on WINOS2.
.
**Problem**
4019 printer does not work correctly with Postscript 39
Font Driver.
**Solution**
Use 17Font Postscript Driver. APAR # PJ03796.
.
**Problem**
4029 printer driver does not work. "Cannot find 300.DRV" error
message appears.
**Solution**
Have the user delete the printer driver from the Windows Control
panel. Then reinstall the driver from the Windows Control
Panel. This will correct the WIN.INI file with the printer
driver information necessary to run correctly. This will be
fixed in a future release of OS/2-2.0, however close any calls
with this problem.
LOCAL FIX: